System and method for processing medical claims using biometric signatures

ABSTRACT

A computer-implemented system for processing medical claims is disclosed. The computer-implemented system includes a medical device configured to be manipulated by a user while the user performs a treatment plan; a patient interface associated with the medical device, the patient interface comprising an output configured to present telemedicine information associated with a telemedicine session; and a processor. The processor is configured to, during the telemedicine session, receive device-generated information from the medical device; generate a first biometric signature; using the device-generated information, generate a second biometric signature; using the first and second biometric signatures, generate a signature comparison; using the signature comparison, generate a signature indicator; and transmit the signature indicator.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. patent application Ser. No. 17/021,895, filed Sep. 15, 2020, titled “Telemedicine for Orthopedic Treatment,” which claims priority to and the benefit of U.S. Provisional Patent Application Ser. No. 62/910,232, filed Oct. 3, 2019, titled “Telemedicine for Orthopedic Treatment,” the entire disclosures of which are hereby incorporated by reference for all purposes. This application also claims priority to and the benefit of U.S. Provisional Patent Application Ser. No. 63/028,420, filed May 21, 2020, titled “System and Method for Processing Medical Claims Using Biometric Signatures,” the entire disclosure of which is hereby incorporated by reference for all purposes.

TECHNICAL FIELD

This disclosure relates generally to systems and methods for processing medical claims using biometric signatures.

BACKGROUND

Electronic medical record (EMR) systems may be used to generate and maintain an electronic record of health-related information relating to or about individuals within a health care organization. The health-related information may be input by a variety of entities, e.g., the individuals' health care providers, where such entries may be made by any medically-related entity or its representatives, for example: administrators, nurses, doctors, or other authorized individuals; insurance companies; billing companies; hospitals; testing centers, such as those related to radiologic services, blood and bodily fluid testing services; and psychological service providers, such as psychologists, social workers, addiction and other counselors, and psychiatrists. Each healthcare service may have one or more medical billing codes, for example, Diagnosis-Related Group (DRG) and/or International Classification of Diseases (ICD) codes, e.g., ICD-10, assigned for billing purposes. Some of the individual's EMRs, including the one or more medical billing codes, may be transferred to a third-party payor, such as an insurance company, for invoicing the individual's medical claims for the individual's healthcare services. A medical claim, or a claim, is a medical bill, or bill, submitted to a health insurance carrier, or other party responsible for payment, for services rendered and/or goods provided to patients by health care providers. After a medical claim is submitted to the insurance company, the insurance company determines its financial responsibility for the payment to the healthcare provider (i.e., claim adjudication). The insurance company may have procedures to ensure that no false medical claims are approved for payment, for example, by rejecting payment for medical billing codes inconsistent with the healthcare services provided. As a result of such procedures, the insurance company may decide to pay the medical claim in full, reduce the medical bill, deny the full medical claim, or revise the nature of the claim such that it becomes eligible for full or partial payment.

Medical billing may present difficulties in claim adjudication when using medical billing codes, often making it difficult for insurance companies to detect whether a particular medical claim is the result of fraud, waste, or abuse. Even if an insurance company has the ability to determine that a medical device has been used, the insurance company may have difficulty in determining whether the use of that medical device was properly billed (e.g., the medical device was not used by or for the patient stated in the medical claim). The use of telemedicine may result in additional risks related to fraud, waste, and abuse, risks which bad actors can exploit. For example, if, at a location other than a healthcare facility, the medical device is being used, a healthcare provider may not oversee the use (e.g., treatment, rehabilitation, or testing), and therefore, the healthcare provider may not be able to easily confirm or validate the accuracy of the medical billing.

SUMMARY

In general, the present disclosure provides a system and method for processing medical claims using biometric signatures.

An aspect of the disclosed embodiments includes a computer-implemented system for processing medical claims. The computer-implemented system includes a medical device configured to be manipulated by a user while the user performs a treatment plan; a patient interface associated with the medical device, the patient interface comprising an output configured to present telemedicine information associated with a telemedicine session; and a processor. The processor is configured to, during the telemedicine session, receive device-generated information from the medical device; generate a first biometric signature; using the device-generated information, generate a second biometric signature; using the first and second biometric signatures, generate a signature comparison; using the signature comparison, generate a signature indicator; and transmit the signature indicator.

An aspect of the disclosed embodiments includes a system for processing medical claims. The system includes a processor configured to receive device-generated information from a medical device; to generate a first biometric signature; to use the device-generated information to generate a second biometric signature; to use the first biometric signature and the second biometric signature to generate a signature comparison; to use the signature comparison to generate a signature indicator; and to transmit the signature indicator.

An aspect of the disclosed embodiments includes a method for processing medical claims. The method includes receiving device-generated information from a medical device. The method further includes generating a first biometric signature; using the device-generated information to generate a second biometric signature; using the first biometric signature and the second biometric signature to generate a signature comparison; using the signature comparison to generate a signature indicator; and transmitting the signature indicator.

An aspect of the disclosed embodiments includes a tangible, non-transitory computer-readable storage medium. The tangible, non-transitory computer-readable storage medium stores instructions that, when executed, cause a processor to receive device-generated information from a medical device. The instructions further cause a processor to generate a first biometric signature; to use the device-generated information to generate a second biometric signature; to use the first biometric signature and the second biometric signature to generate a signature comparison; to use the signature comparison to generate a signature indicator; and to cause the processor to transmit the signature indicator.

Another aspect of the disclosed embodiments includes a system that includes a processing device and a memory communicatively coupled to the processing device and capable of storing instructions. The processing device executes the instructions to perform any of the methods, operations, or steps described herein.

Another aspect of the disclosed embodiments includes a tangible, non-transitory computer-readable medium storing instructions that, when executed, cause a processing device to perform any of the methods, operations, or steps disclosed herein.

Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of this disclosure and its advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings. It is emphasized that, according to common practice, the various features of the drawings are not to-scale. On the contrary, the dimensions of the various features are arbitrarily expanded or reduced for clarity.

FIG. 1 generally illustrates a component diagram of an illustrative medical system according to the principles of this disclosure.

FIG. 2 generally illustrates an example medical device according to the principles of this disclosure.

FIG. 3 generally illustrates a component diagram of an illustrative clinic server system according to the principles of this disclosure.

FIG. 4 generally illustrates a component diagram and method of an illustrative medical claim processing system according to the principles of this disclosure.

FIG. 5 generally illustrates a component diagram of an alternative arrangement of an illustrative medical claim processing system according to the principles of this disclosure.

FIGS. 6A and 6B generally illustrate a method of processing medical claims according to the principles of this disclosure.

FIG. 7 generally illustrates a perspective view of an embodiment of the device, such as a treatment device according to certain aspects of this disclosure.

FIG. 8 generally illustrates a perspective view of a pedal of the treatment device of FIG. 7 according to certain aspects of this disclosure.

FIG. 9 generally illustrates a perspective view of a person using the treatment device of FIG. 7 according to certain aspects of this disclosure.

FIG. 10 generally illustrates an example computer system according to certain aspects of this disclosure.

NOTATION AND NOMENCLATURE

Various terms are used to refer to particular system components. Different companies may refer to a component by different names—this document does not intend to distinguish between components that differ in name but not function. In the following discussion and in the claims, the terms “including” and “comprising” are used in an open-ended fashion, and thus should be interpreted to mean “including, but not limited to . . . .” Also, the term “couple” or “couples” is intended to mean either an indirect or direct connection. Thus, if a first device couples to a second device, that connection may be through a direct connection or through an indirect connection via other devices and connections.

The terminology used herein is for the purpose of describing particular example embodiments only, and is not intended to be limiting. As used herein, the singular forms “a,” “an,” and “the” may be intended to include the plural forms as well, unless the context clearly indicates otherwise. The method steps, processes, and operations described herein are not to be construed as necessarily requiring their performance in the particular order discussed or illustrated, unless specifically identified as an order of performance. It is also to be understood that additional or alternative steps may be employed.

The terms first, second, third, etc. may be used herein to describe various elements, components, regions, layers and/or sections; however, these elements, components, regions, layers and/or sections should not be limited by these terms. These terms may be only used to distinguish one element, component, region, layer, or section from another region, layer, or section. Terms such as “first,” “second,” and other numerical terms, when used herein, do not imply a sequence or order unless clearly indicated by the context. Thus, a first element, component, region, layer, or section discussed below could be termed a second element, component, region, layer, or section without departing from the teachings of the example embodiments. The phrase “at least one of,” when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, “at least one of: A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C. In another example, the phrase “one or more” when used with a list of items means there may be one item or any suitable number of items exceeding one.

Spatially relative terms, such as “inner,” “outer,” “beneath,” “below,” “lower,” “above,” “upper,” “top,” “bottom,” “inside,” “outside,” “contained within,” “superimposing upon,” and the like, may be used herein. These spatially relative terms can be used for ease of description to describe one element's or feature's relationship to another element(s) or feature(s) as illustrated in the figures. The spatially relative terms may also be intended to encompass different orientations of the device in use, or operation, in addition to the orientation depicted in the figures. For example, if the device in the figures is turned over, elements described as “below” or “beneath” other elements or features would then be oriented “above” the other elements or features. Thus, the example term “below” can encompass both an orientation of above and below. The device may be otherwise oriented (rotated 90 degrees or at other orientations) and the spatially relative descriptions used herein interpreted accordingly.

A “treatment plan” may include one or more treatment protocols, and each treatment protocol includes one or more treatment sessions. Each treatment session comprises several session periods, with each session period including a particular exercise for treating the body part of the patient. For example, a treatment plan for post-operative rehabilitation after a knee surgery may include an initial treatment protocol with twice daily stretching sessions for the first 3 days after surgery and a more intensive treatment protocol with active exercise sessions performed 4 times per day starting 4 days after surgery. A treatment plan may also include information pertaining to a medical procedure to perform on the patient, a treatment protocol for the patient using a treatment device, a diet regimen for the patient, a medication regimen for the patient, a sleep regimen for the patient, additional regimens, or some combination thereof.

The terms telemedicine, telehealth, telemed, teletherapeutic, telemedicine, remote medicine, etc. may be used interchangeably herein.

The term “optimal treatment plan” may refer to optimizing a treatment plan based on a certain parameter or factors or combinations of more than one parameter or factor, such as, but not limited to, a measure of benefit which one or more exercise regimens provide to users, one or more probabilities of users complying with one or more exercise regimens, an amount, quality or other measure of sleep associated with the user, information pertaining to a diet of the user, information pertaining to an eating schedule of the user, information pertaining to an age of the user, information pertaining to a sex of the user, information pertaining to a gender of the user, an indication of a mental state of the user, information pertaining to a genetic condition of the user, information pertaining to a disease state of the user, an indication of an energy level of the user, information pertaining to a microbiome from one or more locations on or in the user (e.g., skin, scalp, digestive tract, vascular system, etc.), or some combination thereof.

As used herein, the term healthcare provider may include a medical professional (e.g., such as a doctor, a nurse, a therapist, and the like), an exercise professional (e.g., such as a coach, a trainer, a nutritionist, and the like), or another professional sharing at least one of medical and exercise attributes (e.g., such as an exercise physiologist, a physical therapist, an occupational therapist, and the like). As used herein, and without limiting the foregoing, a “healthcare provider” may be a human being, a robot, a virtual assistant, a virtual assistant in virtual and/or augmented reality, or an artificially intelligent entity, such entity including a software program, integrated software and hardware, or hardware alone.

Real-time may refer to less than or equal to 2 seconds. Near real-time may refer to any interaction of a sufficiently short time to enable two individuals to engage in a dialogue via such user interface, and will preferably but not determinatively be less than 10 seconds (or any suitably proximate difference between two different times) but greater than 2 seconds.

Any of the systems and methods described in this disclosure may be used in connection with rehabilitation. Rehabilitation may be directed at cardiac rehabilitation, rehabilitation from stroke, multiple sclerosis, Parkinson's disease, myasthenia gravis, Alzheimer's disease, any other neurodegenative or neuromuscular disease, a brain injury, a spinal cord injury, a spinal cord disease, a joint injury, a joint disease, post-surgical recovery, or the like. Rehabilitation can further involve muscular contraction in order to improve blood flow and lymphatic flow, engage the brain and nervous system to control and affect a traumatized area to increase the speed of healing, reverse or reduce pain (including arthralgias and myalgias), reverse or reduce stiffness, recover range of motion, encourage cardiovascular engagement to stimulate the release of pain-blocking hormones or to encourage highly oxygenated blood flow to aid in an overall feeling of well-being. Rehabilitation may be provided for individuals of average weight in reasonably good physical condition having no substantial deformities, as well as for individuals more typically in need of rehabilitation, such as those who are elderly, obese, subject to disease processes, injured and/or who have a severely limited range of motion. Unless expressly stated otherwise, is to be understood that rehabilitation includes prehabilitation (also referred to as “pre-habilitation” or “prehab”). Prehabilitation may be used as a preventative procedure or as a pre-surgical or pre-treatment procedure. Prehabilitation may include any action performed by or on a patient (or directed to be performed by or on a patient, including, without limitation, remotely or distally through telemedicine) to, without limitation, prevent or reduce a likelihood of injury (e.g., prior to the occurrence of the injury); improve recovery time subsequent to surgery; improve strength subsequent to surgery; or any of the foregoing with respect to any non-surgical clinical treatment plan to be undertaken for the purpose of ameliorating or mitigating injury, dysfunction, or other negative consequence of surgical or non-surgical treatment on any external or internal part of a patient's body. For example, a mastectomy may require prehabilitation to strengthen muscles or muscle groups affected directly or indirectly by the mastectomy. As a further non-limiting example, the removal of an intestinal tumor, the repair of a hernia, open-heart surgery or other procedures performed on internal organs or structures, whether to repair those organs or structures, to excise them or parts of them, to treat them, etc., can require cutting through, dissecting and/or harming numerous muscles and muscle groups in or about, without limitation, the skull or face, the abdomen, the ribs and/or the thoracic cavity, as well as in or about all joints and appendages. Prehabilitation can improve a patient's speed of recovery, measure of quality of life, level of pain, etc. in all the foregoing procedures. In one embodiment of prehabilitation, a pre-surgical procedure or a pre-non-surgical-treatment may include one or more sets of exercises for a patient to perform prior to such procedure or treatment. Performance of the one or more sets of exercises may be required in order to qualify for an elective surgery, such as a knee replacement. The patient may prepare an area of his or her body for the surgical procedure by performing the one or more sets of exercises, thereby strengthening muscle groups, improving existing muscle memory, reducing pain, reducing stiffness, establishing new muscle memory, enhancing mobility (i.e., improve range of motion), improving blood flow, and/or the like.

The phrase, and all permutations of the phrase, “respective measure of benefit with which one or more exercise regimens may provide the user” (e.g., “measure of benefit,” “respective measures of benefit,” “measures of benefit,” “measure of exercise regimen benefit,” “exercise regimen benefit measurement,” etc.) may refer to one or more measures of benefit with which one or more exercise regimens may provide the user.

DETAILED DESCRIPTION

The following discussion is directed to various embodiments of the present disclosure. Although one or more of these embodiments may be preferred, the embodiments disclosed should not be interpreted, or otherwise used, as limiting the scope of the disclosure, including the claims. In addition, one skilled in the art will understand that the following description has broad application, and the discussion of any embodiment is meant only to be exemplary of that embodiment, and not intended to intimate that the scope of the disclosure, including the claims, is limited to that embodiment.

Determining optimal remote examination procedures to create an optimal treatment plan for a patient having certain characteristics (e.g., vital-sign or other measurements; performance; demographic; psychographic; geographic; diagnostic; measurement- or test-based; medically historic; behavioral historic; cognitive; etiologic; cohort-associative; differentially diagnostic; surgical, physically therapeutic, pharmacologic and other treatment(s) recommended; etc.) may be a technically challenging problem. For example, a multitude of information may be considered when determining a treatment plan, which may result in inefficiencies and inaccuracies in the treatment plan selection process. In a rehabilitative setting, some of the multitude of information considered may include characteristics of the patient such as personal information, performance information, and measurement information. The personal information may include, e.g., demographic, psychographic or other information, such as an age, a weight, a gender, a height, a body mass index, a medical condition, a familial medication history, an injury, a medical procedure, a medication prescribed, or some combination thereof. The performance information may include, e.g., an elapsed time of using a treatment device, an amount of force exerted on a portion of the treatment device, a range of motion achieved on the treatment device, a movement speed of a portion of the treatment device, a duration of use of the treatment device, an indication of a plurality of pain levels using the treatment device, or some combination thereof. The measurement information may include, e.g., a vital sign, a respiration rate, a heartrate, a temperature, a blood pressure, a glucose level or other biomarker, or some combination thereof. It may be desirable to process and analyze the characteristics of a multitude of patients, the treatment plans performed for those patients, and the results of the treatment plans for those patients.

Further, another technical problem may involve distally treating, via a computing device during a telemedicine session, a patient from a location different than a location at which the patient is located. An additional technical problem is controlling or enabling, from the different location, the control of a treatment device used by the patient at the patient's location. Oftentimes, when a patient undergoes rehabilitative surgery (e.g., knee surgery), a medical professional may prescribe a treatment device to the patient to use to perform a treatment protocol at their residence or at any mobile location or temporary domicile. A medical professional may refer to a doctor, physician assistant, nurse, chiropractor, dentist, physical therapist, acupuncturist, physical trainer, or the like. A medical professional may refer to any person with a credential, license, degree, or the like in the field of medicine, physical therapy, rehabilitation, or the like.

When the healthcare provider is located in a location different from the patient and the treatment device, it may be technically challenging for the healthcare provider to monitor the patient's actual progress (as opposed to relying on the patient's word about their progress) in using the treatment device, modify the treatment plan according to the patient's progress, adapt the treatment device to the personal characteristics of the patient as the patient performs the treatment plan, and the like.

Further, in addition to the information described above, determining optimal examination procedures for a particular ailment (e.g., injury, disease, any applicable medical condition, etc.) may include physically examining the injured body part of a patient. The healthcare provider, such as a physician or a physical therapist, may visually inspect the injured body part (e.g., a knee joint). The inspection may include looking for signs of inflammation or injury (e.g., swelling, redness, and warmth), deformity (e.g., symmetrical joints and abnormal contours and/or appearance), or any other suitable observation. To determine limitations of the injured body part, the healthcare provider may observe the injured body part as the patient attempts to perform normal activity (e.g., bending and extending the knee and gauging any limitations to the range of motion of the injured knee). The healthcare provide may use one or more hands and/or fingers to touch the injured body part. By applying pressure to the injured body part, the healthcare provider can obtain information pertaining to the extent of the injury. For example, the healthcare provider's fingers may palpate the injured body part to determine if there is point tenderness, warmth, weakness, strength, or to make any other suitable observation.

It may be desirable to compare characteristics of the injured body part with characteristics of a corresponding non-injured body part to determine what an optimal treatment plan for the patient may be such that the patient can obtain a desired result. Thus, the healthcare provider may examine a corresponding non-injured body part of the patient. For example, the healthcare provider's fingers may palpate a non-injured body part (e.g., a left knee) to determine a baseline of how the patient's non-injured body part feels and functions. The healthcare provider may use the results of the examination of the non-injured body part to determine the extent of the injury to the corresponding injured body part (e.g., a right knee). Additionally, injured body parts may affect other body parts (e.g., a knee injury may limit the use of the affected leg, leading to atrophy of leg muscles). Thus, the healthcare provider may also examine additional body parts of the patient for evidence of atrophy of or injury to surrounding ligaments, tendons, bones, and muscles, examples of muscles being such as quadriceps, hamstrings, or calf muscle groups of the leg with the knee injury. The healthcare provider may also obtain information as to a pain level of the patient before, during, and/or after the examination.

The healthcare provider can use the information obtained from the examination (e.g., the results of the examination) to determine a proper treatment plan for the patient. If the healthcare provider cannot conduct a physical examination of the one or more body parts of the patient, the healthcare provider may not be able to fully assess the patient's injury and the treatment plan may not be optimal. Accordingly, embodiments of the present disclosure pertain to systems and methods for conducting a remote examination of a patient. The remote examination system provides the healthcare provider with the ability to conduct a remote examination of the patient, not only by communicating with the patient, but by virtually observing and/or feeling the patient's one or more body parts.

In some embodiments, the systems and methods described herein may be configured for manipulation of a medical device. For example, the systems and methods may be configured to use a medical device configured to be manipulated by an individual while the individual is performing a treatment plan. The individual may include a user, patient, or other a person using the treatment device to perform various exercises for prehabilitation, rehabilitation, stretch training, e.g., pliability, medical procedures, and the like. The systems and methods described herein may be configured to use and/or provide a patient interface comprising an output device, wherein the output device is configured to present telemedicine information associated with a telemedicine session.

In some embodiments, the systems and methods described herein may be configured for processing medical claims. For example, the system includes a processor configured to receive device-generated information from a medical device. Using the device-generated information received, the processor is configured to determine device-based medical coding information. The processor is further configured to transmit the device-based medical coding information to a claim adjudication server. Any or all of the methods described may be implemented during a telemedicine session or at any other desired time.

In some embodiments, the medical claims may be processed, during a telemedicine or telehealth session, by a healthcare provider. The healthcare provider may select a particular treatment plan for the patient to cause that treatment plan to be transmitted to the patient and/or to control, based on the treatment plan, the treatment device. In some embodiments, to facilitate telehealth or telemedicine applications, including remote diagnoses, determination of treatment plans and rehabilitative and/or pharmacologic prescriptions, the artificial intelligence engine may receive data, instruct ructions, or the like and/or operate distally from the patient and the treatment device.

In such cases, the recommended treatment plans and/or excluded treatment plans may be presented simultaneously with a video of the patient in real-time or near real-time during a telemedicine or telehealth session on a user interface of a computing device of a medical professional. The video may also be accompanied by audio, text and other multimedia information and/or other sensorial or perceptive (e.g., tactile, gustatory, haptic, pressure-sensing-based or electromagnetic (e.g., neurostimulation), and without limitation, gesture recognition, gesture control, touchless user interfaces (TUIs), kinetic user interfaces (KUIs), tangible user interfaces, wired gloves, depth-aware cameras, stereo cameras, and gesture-based controllers). Real-time may refer to less than or equal to 2 seconds. Near real-time may refer to any interaction of a sufficiently short time to enable two individuals to engage in a dialogue via such user interface, and will generally be less than 10 seconds (or any suitably proximate difference between two different times) but greater than 2 seconds.

FIGS. 1-10, discussed below, and the various embodiments used to describe the principles of this disclosure are by way of illustration only and should not be construed in any way to limit the scope of the disclosure.

FIG. 1 illustrates a component diagram of an illustrative medical system 100 in accordance with aspects of this disclosure. The medical system 100 may include a medical device 102. The medical device 102 may be a testing device, a diagnostic device, a therapeutic device, or any other suitable medical device. “Medical device” as used in this context means any hardware, software, mechanical, such as a treatment device (e.g., medical device 102, treatment device 10, or the like), that may assist in a medical service, regardless of whether it is FDA (or other governmental regulatory body of any given country) approved, required to be FDA (or other governmental regulatory body of any given country) approved or available commercially or to consumers without such approval. Non-limiting examples of medical devices include a thermometer, an MRI machine, a CT-scan machine, a glucose meter, an apheresis machine, and a physical therapy machine, such as a physical therapy cycle. Non-limiting examples of places where the medical device 102 may be located include a healthcare clinic, a physical rehabilitation center, and a user's home to allow for telemedicine treatment, rehabilitation, and/or testing. FIG. 2 illustrates an example of the medical device 102 where the medical device 102 is a physical therapy cycle.

As generally illustrated in FIG. 2, the medical device 102 may comprise an electromechanical device, such as a physical therapy device. FIG. 2 generally illustrates a perspective view of an example of a medical device 102 according to certain aspects of this disclosure. Specifically, the medical device 102 illustrated is an electromechanical device 202, such as an exercise and rehabilitation device (e.g., a physical therapy device or the like). The electromechanical device 202 is shown having pedal 210 on opposite sides that are adjustably positionable relative to one another on respective radially-adjustable couplings 208. The depicted electromechanical device 202 is configured as a small and portable unit so that it is easily transported to different locations at which rehabilitation or treatment is to be provided, such as at patients' homes, alternative care facilities, or the like. The patient may sit in a chair proximate the electromechanical device 202 to engage the electromechanical device 202 with the patient's feet, for example. The electromechanical device 202 includes a rotary device such as radially-adjustable couplings 208 or flywheel or the like rotatably mounted such as by a central hub to a frame or other support. The pedals 210 are configured for interacting with a patient to be rehabilitated and may be configured for use with lower body extremities such as the feet, legs, or upper body extremities, such as the hands, arms, and the like. For example, the pedal 210 may be a bicycle pedal of the type having a foot support rotatably mounted onto an axle with bearings. The axle may or may not have exposed end threads for engaging a mount on the radially-adjustable coupling 208 to locate the pedal on the radially-adjustable coupling 208. The radially-adjustable coupling 208 may include an actuator configured to radially adjust the location of the pedal to various positions on the radially-adjustable coupling 208.

Alternatively, the radially-adjustable coupling 208 may be configured to have both pedals 210 on opposite sides of a single coupling 208. In some embodiments, as depicted, a pair of radially-adjustable couplings 208 may be spaced apart from one another but interconnected to an electric motor 206. In the depicted example, the computing device 112 may be mounted on the frame of the electromechanical device 202 and may be detachable and held by the user while the user operates the electromechanical device 202. The computing device 112 may present the patient portal 212 and control the operation of the electric motor 206, as described herein.

In some embodiments, as described in U.S. Pat. No. 10,173,094 (U.S. application Ser. No. 15/700,293), which is incorporated by reference herein in its entirety for all purposes, the medical device 102 may take the form of a traditional exercise/rehabilitation device which is more or less non-portable and remains in a fixed location, such as a rehabilitation clinic or medical practice. The medical device 102 may include a seat and is less portable than the medical device 102 shown in FIG. 2. FIG. 2 is not intended to be limiting; the electromechanical device 202 may include more or fewer components than those illustrated in FIG. 2.

FIGS. 7-8 generally illustrate an embodiment of a treatment device, such as a treatment device 10. More specifically, FIG. 7 generally illustrates a treatment device 10 in the form of an electromechanical device, such as a stationary cycling machine 14, which may be called a stationary bike, for short. The stationary cycling machine 14 includes a set of pedals 12 each attached to a pedal arm 20 for rotation about an axle 16. In some embodiments, and as generally illustrated in FIG. 8, the pedals 12 are movable on the pedal arm 20 in order to adjust a range of motion used by the patient in pedaling. For example, the pedals being located inwardly toward the axle 16 corresponds to a smaller range of motion than when the pedals are located outwardly away from the axle 16. A pressure sensor 18 is attached to or embedded within one of the pedals 12 for measuring an amount of force applied by the patient on the pedal 102. The pressure sensor 18 may communicate wirelessly to the treatment device 10 and/or to the patient interface 26. FIGS. 7-8 are not intended to be limiting; the treatment device 10 may include more or fewer components than those illustrated in FIGS. 7-8.

FIG. 9 generally illustrates a person (a patient) using the treatment device 10 of FIG. 7, and showing sensors and various data parameters connected to a patient interface 26. The example patient interface 26 is a tablet computer or smartphone, or a phablet, such as an iPad, an iPhone, an Android device, or a Surface tablet, which is held manually by the patient. In some other embodiments, the patient interface 26 may be embedded within or attached to the treatment device 10. FIG. 9 generally illustrates the patient wearing the ambulation sensor 22 on his wrist, with a note showing “STEPS TODAY 1355”, indicating that the ambulation sensor 22 has recorded and transmitted that step count to the patient interface 26. FIG. 9 also generally illustrates the patient wearing the goniometer 24 on his right knee, with a note showing “KNEE ANGLE 72°”, indicating that the goniometer 24 is measuring and transmitting that knee angle to the patient interface 26. FIG. 9 generally illustrates a right side of one of the pedals 12 with a pressure sensor 18 showing “FORCE 12.5 lbs.”, indicating that the right pedal pressure sensor 18 is measuring and transmitting that force measurement to the patient interface 26. FIG. 9 also generally illustrates a left side of one of the pedals 12 with a pressure sensor 18 showing “FORCE 27 lbs.”, indicating that the left pedal pressure sensor 18 is measuring and transmitting that force measurement to the patient interface 26. FIG. 9 also generally illustrates other patient data, such as an indicator of “SESSION TIME 0:04:13”, indicating that the patient has been using the treatment device 10 for 4 minutes and 13 seconds. This session time may be determined by the patient interface 26 based on information received from the treatment device 10. FIG. 9 also generally illustrates an indicator showing “PAIN LEVEL 3”, Such a pain level may be obtained from the patient in response to a solicitation, such as a question, presented upon the patient interface 26.

The medical device 102 may include an electromechanical device 104, such as pedals of a physical therapy cycle, a goniometer configured to attach to a joint and measure joint angles, or any other suitable electromechanical device 104. The electromechanical device 104 may be configured to transmit information, such as positioning information. A non-limiting example of positioning information includes information relating to the location of pedals of the physical therapy cycle 200. The medical device 102 may include a sensor 106. The sensor 106 can be used for obtaining information to be used in generating a biometric signature. A biometric signature, for the purpose of this disclosure, is a signature derived from certain biological characteristics of a user. The biometric signature can include information of a user, such as fingerprint information, retina information, voice information, height information, weight information, vital sign information (e.g., blood pressure, heart rate, etc.), response information to physical stimuli (e.g., change in heart rate while running on a treadmill), performance information (rate of speed on the electromechanical device 104), or any other suitable biological characteristic(s) of the user. The biometric signature may include and/or be determined by a kinesiological signature. A kinesiological signature, for the purpose of this disclosure, refers to a signature derived from human body movement, such as information about a range of motion of or about a user's joint, e.g., a knee, an elbow, a neck, a spine, or any other suitable joint, ligament, tendon, or muscle of a human. The sensor 106 may be a temperature sensor (such as a thermometer or thermocouple), a strain gauge, a proximity sensor, an accelerometer, an inclinometer, an infrared sensor, a pressure sensor, a light sensor, a smoke sensor, a chemical sensor, any other suitable sensor, a fingerprint scanner, a sound sensor, a microphone, or any combination thereof. The medical device 102 may include, for obtaining information to be used in generating a biometric signature, a camera 108, such as a still image camera, a video camera, an infrared camera, an X-ray camera, any other suitable camera, or any combination thereof. The medical device 102 may include, for obtaining information to be used in generating a biometric signature, an imaging device 110, such as an MM imaging device, an X-ray imaging device, a thermal imaging device, any other suitable imaging device, or any combination thereof.

The medical device 102 may include, be coupled to, or be in communication with a computing device 112. The computing device 112 may include a processor 114. The processor 114 can include, for example, computers, intellectual property (IP) cores, application-specific integrated circuits (ASICs), programmable logic arrays, optical processors, programmable logic controllers, microcode, microcontrollers, servers, microprocessors, digital signal processors, any other suitable circuit, or any combination thereof.

The computing device 112 may include a memory device 116 in communication with the processor 114. The memory device 116 can include any type of memory capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a flash drive, a compact disc (CD), a digital video disc (DVD), solid state drive (SSD), or any other suitable type of memory.

The computing device 112 may include an input device 118 in communication with the processor 114. Examples of the input device 118 include a keyboard, a keypad, a mouse, a microphone supported by speech-to-text software, or any other suitable input device. The input device 118 may be used by a medical system operator to input information, such as user-identifying information, observational notes, or any other suitable information. An operator is to be understood throughout this disclosure to include both people and computer software, such as programs or artificial intelligence.

The computing device 112 may include an output device 120 in communication with the processor 114. The output device 120 may be used to provide information to the medical device operator or a user of the medical device 102. Examples of the output device 120 may include a display screen, a speaker, an alarm system, or any other suitable output device, including haptic, tactile, olfactory, or gustatory ones, and without limitation, gesture recognition, gesture control, touchless user interfaces (TUIs), kinetic user interfaces (KUIs), tangible user interfaces, wired gloves, depth-aware cameras, stereo cameras, and gesture-based controllers. In some embodiments, such as where the computing device 112 includes a touchscreen, the input device 118 and the output device 120 may be the same device.

For communicating with remote computers and servers, the computing device 112 may include a network adapter 122 in communication with the processor 114. The network adapter 122 may include wired or wireless network adapter devices or a wired network port.

Any time information is transmitted or communicated, the information may be in EDI file format or any other suitable file format. In any of the methods or steps of the method, file format conversions may take place. By utilizing Internet of Things (IoT) gateways, data streams, ETL bucketing, EDI mastering, or any other suitable technique, data can be mapped, converted, or transformed into a carrier preferred state. As a result of the volume of data being transmitted, the data security requirements, and the data consistency requirements, enterprise grade architecture may be utilized for reliable data transfer.

FIG. 1 is not intended to be limiting; the medical system 100 and the computing device 112 may include more or fewer components than those illustrated in FIG. 1.

FIG. 3 illustrates a component diagram of an illustrative clinic server system 300 in accordance with aspects of this disclosure. The clinic server system 300 may include a clinic server 302. The clinic server system 300 or clinic server 302 may be servers owned or controlled by a medical clinic (such as a doctor's office, testing site, or therapy clinic) or by a medical practice group (such as a testing company, outpatient procedure clinic, diagnostic company, or hospital). The clinic server 302 may be proximate to the medical system 100. In other embodiments, the clinic server 302 may be remote from the medical system 100. For example, during telemedicine-based or telemedicine-mediated treatment, rehabilitation, or testing, the clinic server 302 may be located at a healthcare clinic and the medical system 100 may be located at a patient's home. The clinic server 302 may be a rackmount server, a router computer, a personal computer, a portable digital assistant, a smartphone, a laptop computer, a tablet computer, a netbook, a desktop computer, any other suitable computing device, or any combination of the above. The clinic server 302 may be cloud-based or be a real-time software platform, and it may include privacy (e.g., anonymization, pseudonymization, or other) software or protocols, and/or include security software or protocols. The clinic server 302 may include a computing device 304. The computing device 304 may include a processor 306. The processor 306 can include, for example, computers, intellectual property (IP) cores, application-specific integrated circuits (ASICs), programmable logic arrays, optical processors, programmable logic controllers, microcode, microcontrollers, servers, microprocessors, digital signal processors, any other suitable circuit, or any combination thereof.

The computing device 304 may include a memory device 308 in communication with the processor 306. The memory device 308 can include any type of memory capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a flash drive, a compact disc (CD), a digital video disc (DVD), a solid state drive (SSD), or any other suitable type of memory.

The computing device 304 may include an input device 310 in communication with the processor 306. Examples of the input device 310 include a keyboard, a keypad, a mouse, a microphone supported by speech-to-text software, or any other suitable input device.

The computing device 304 may include an output device 312 in communication with the processor 114. Examples of the output device 312 include a display screen, a speaker, an alarm system, or any other suitable output device, including haptic, tactile, olfactory, or gustatory ones, and without limitation, gesture recognition, gesture control, touchless user interfaces (TUIs), kinetic user interfaces (KUIs), tangible user interfaces, wired gloves, depth-aware cameras, stereo cameras, and gesture-based controllers. In some embodiments, such as where the computing device 304 includes a touchscreen, the input device 310 and the output device 312 may be the same device.

The computing device 304 may include a network adapter 314 in communication with the processor 306 for communicating with remote computers and/or servers. The network adapter 314 may include wired or wireless network adapter devices.

FIG. 3 is not intended to be limiting; the clinic server system 300, the clinic server 302, and the computing device 304 may include more or fewer components than those illustrated in FIG. 3.

FIG. 4 illustrates a component diagram and method of an illustrative medical claim processing system 400 and information flow according to aspects of this disclosure. The medical claim processing system 400 may include the medical system 100. The medical claim processing system 400 may include a clinic server 302.

The medical claim processing system 400 may include a patient notes database 402. The patient notes database 402 may include information input by a clinic operator or information received from the clinic server 302. For example, the clinic operator may enter information obtained manually about a patient's height and weight and/or information received from the patient about a condition from which the patient is suffering. The medical claim processing system 400 may include an electronic medical records (EMR) database 404. The EMR database 404 may include information input by a clinic operator and/or information received from the clinic server 302 or the patient notes database 402. For example, the EMR database 404 may contain information received from the medical devices 102 or historical information obtained from patient notes database 402, such as historical height and weight information. One or both of the patient notes database 402 and the EMR database 404 may be located on the clinic server 302, on one or more remote servers, or on any other suitable system or server.

The medical claim processing system 400 may include a biller server 406. The biller server 406 may receive medical service information from the medical system 100; the clinic server 302; the patient notes database 402; the EMR database 404; any suitable system, server, or database; or any combination thereof. The medical service information may include medical coding information. By correlating the medical service information with an associated medical code, the biller server 406 may determine medical coding information. The biller server 406 may determine one or more responsible parties for payment of medical bills. Using the medical codes, the biller server 406 may generate an invoice. The biller server 406 may transmit the medical coding information and medical service information to the responsible party or parties. The biller server 406 may be owned or controlled by a medical practice group (such as a testing company, an outpatient procedure clinic, a diagnostic company, or a hospital), a health insurance company, a governmental entity, or any other organization (including third-party organizations) associated with medical billing procedures. The biller server 406 may be a rackmount server, a router computer, a personal computer, a portable digital assistant, a smartphone, a laptop computer, a tablet computer, a netbook, a desktop computer, any other suitable computing device, or any combination of the above. The biller server 406 may be cloud-based or be a real-time software platform, and it may include privacy (e.g., anonymization, pseudonymization, or other) software or protocols, and/or include security software or protocols. The biller server 406 may contain a computing device including any combination of the components of the computing device 304 as illustrated in FIG. 3. The biller server 406 may be proximate to or remote from the clinic server 302.

The medical claim processing system 400 may include a claim adjudication server 408. The claim adjudication server 408 may be owned or controlled by a health insurance company, governmental entity, or any other organization (including third-party organizations) associated with medical billing procedures. The claim adjudication server 408 may be a rackmount server, a router computer, a personal computer, a portable digital assistant, a smartphone, a laptop computer, a tablet computer, a netbook, a desktop computer, any other suitable computing device, or any combination of the above. The claim adjudication server 408 may be cloud-based or be a real-time software platform, and it may include privacy (e.g., anonymization, pseudonymization, or other) software or protocols, and/or include security software or protocols. The claim adjudication server 408 may contain a computing device including any combination of the components of the computing device 304 as illustrated in FIG. 3. The claim adjudication server 408 may be proximate to or remote from the biller server 406. The claim adjudication server 408 may be configured to make or receive a determination about whether a claim should be paid.

The medical claim processing system 400 may include a fraud, waste, and abuse (FWA) server 410. The FWA server 410 may be owned or controlled by a health insurance company, a governmental entity, or any other organization (including a third-party organization) associated with medical billing procedures. The FWA server 410 may be a rackmount server, a router computer, a personal computer, a portable digital assistant, a smartphone, a laptop computer, a tablet computer, a netbook, a desktop computer, any other suitable computing device, or any combination of the above. The FWA server 410 may be cloud-based or be a real-time software platform, and it may include privacy-enhancing, privacy-preserving, or privacy modifying software or protocols (e.g., anonymization, pseudonymization, or other), and/or include security software or protocols. The FWA server 410 may contain a computing device including any combination of the components of the computing device 304 as illustrated in FIG. 3. The FWA server 410 may be proximate to or remote from the claim adjudication server 408. The FWA server 410 may be configured to make or receive a determination about whether a medical claim should be paid. The FWA server 410 may be configured to make or receive a determination about whether a proposed payment for a medical claim is a result of fraud, waste, or abuse.

The medical claim processing system 400 may include a payment server 412. The payment server 412 may be owned or controlled by a health insurance company, a governmental entity, or any other organization (including a third-party organization) associated with medical billing procedures. The payment server 412 may be a rackmount server, a router computer, a personal computer, a portable digital assistant, a smartphone, a laptop computer, a tablet computer, a netbook, a desktop computer, any other suitable computing device, or any combination of the above. The payment server 412 may be cloud-based or be a real-time software platform, and it may include privacy-enhancing, privacy-preserving, or privacy modifying software or protocols (e.g., anonymization, pseudonymization, or other), and/or include security software or protocols. The payment server 412 may contain a computing device including any combination of the components of the computing device 304. The payment server 412 may be proximate to or remote from the biller server 406 and/or the FWA server 410. The payment server 412 may be configured to make or receive a determination about whether a claim should be paid. The payment server 412 may be configured to make or receive a determination about whether a proposed payment is, wholly or partially, a direct or indirect result of fraud, waste, or abuse. The payment server 412 may be configured to process or transmit a payment to the service provider.

FIG. 4 is not intended to be limiting; the medical claim processing system 400 and any sub-components thereof may include more or fewer components, steps, and/or processes than those illustrated in FIG. 4. Any of the components of the medical claim processing system 400 may be in direct or indirect communication with each other. Any or all of the methods described may be implemented during a telemedicine session or at any other desired time.

FIG. 5 illustrates a component diagram of an illustrative medical claim processing system 500 according to aspects of this disclosure. The medical claim processing system 500 can include the medical system 100 of FIG. 1. The medical system 100 may be in communication with a network 502. The network 502 may be a public network (e.g., connected to the Internet via wired (Ethernet) or wireless (Wi-Fi)), a private network (e.g., a local area network (LAN) or a wide area network (WAN)), a combination thereof, or any other suitable network.

The medical claim processing system 500 can include the clinic server 302. The clinic server 302 may be in communication with the network 502. The clinic server 302 is shown as an example of servers that can be in communication with the network 502. In addition to or in place of the clinic server 302, the medical claim processing system 500 can include the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, or any combination thereof.

The medical claim processing system 500 can include a cloud-based learning system 504. For example, the cloud-based learning system 504 may be used to update or change a first biometric signature (i.e., a predicted biometric signature) of a user using historical device-based signature information relating to the user or other users, such as those with similar medical conditions, medical services provided, demographics, or any other suitable similarity. The cloud-based learning system 504 may be used to update or change an algorithm for generating a signature indicator. The signature indicator can include whether the first biometric signature (i.e., the predicted biometric signature) matches a second biometric signature (i.e., a device-based biometric signature). Examples of signature indicators include flags and computer-coded variables. The cloud-based learning system 504 may be in communication with the network 502. The cloud-based learning system 504 may include one or more training servers 506 and form a distributed computing architecture. Each of the training servers 506 may include a computing device, including any combination of one or more of the components of the computing device 304 as illustrated in FIG. 3, or any other suitable components. The training servers 506 may be in communication with one another via any suitable communication protocol. The training servers 506 may store profiles for users including, but not limited to, patients, clinics, practice groups, and/or insurers. The profiles may include information such as historical device-generated information, historical device-based medical coding information, historical reviewed medical coding information, historical electronic medical records (EMRs), historical predicted biometric signatures, historical device-based biometric signatures, historical signature comparisons, historical signature indicators, historical emergency biometric signatures, historical emergency comparisons, historical emergency indicators, and any other suitable historical information. Other non-limiting examples of suitable historical information can include any information relating to a specific patient, a condition, or a population that was recorded at a time prior to the interaction presently being billed as the medical claim.

In some aspects, the cloud-based learning system 504 may include a training engine 508 capable of generating one or more machine learning models 510. The machine learning models 510 may be trained to generate algorithms that aid in determining the device-based medical coding information, for example, by using the device generated information or generation of predicted biometric signatures, device-based biometric signatures, signature indicators, emergency biometric signatures, and/or emergency indicators. For example, if the medical device 102 is an MRI machine, the machine learning models 510 may use the device-generated information generated by the MRI machine (e.g., MRI images) to generate progressively more accurate algorithms to determine which type of medical procedure (e.g., MM scan) was performed and which type of medical coding information (e.g., 73720, 73723, and 74183) to associate with the medical procedure performed, predicted biometric signatures, and/or signature indicators. To generate the one or more machine learning models 510, the training engine 508 may train the one or more machine learning models 510. The training engine 508 may use a base data set of historical device-generated information (e.g., generated from the medical device), historical device-based medical coding information, historical reviewed medical coding information, historical electronic medical records (EMRs), historical predicted biometric signatures, historical device-based biometric signatures, historical signature comparisons, historical signature indicators, historical emergency biometric signatures, historical emergency comparisons, historical emergency indicators, and any other suitable historical information. The training engine 508 may be in communication with the training servers 506. The training engine 508 may be located on the training servers 506.

The training engine 508 may be a rackmount server, a router computer, a personal computer, a portable digital assistant, a smartphone, a laptop computer, a tablet computer, a netbook, a desktop computer, an Internet of Things (IoT) node or sensor, any other suitable computing device, or any combination of the above. The training engine 508 may be cloud-based or be a real-time software platform, and it may include privacy-enhancing, privacy-preserving, or privacy modifying software or protocols (e.g., anonymization, pseudonymization, or other), and/or include security software or protocols. Using training data that includes training inputs and corresponding target outputs, the one or more machine learning models 510 may refer to model artifacts created by the training engine 508. The training engine 508 may find patterns in the training data that map the training input to the target output and generate the machine learning models 510 that identify, store, or use these patterns. Although depicted separately from the medical system 100, the clinic server 302, the biller server 406, the claim adjudication server 408, the training engine 508, and the machine learning models 510 may reside on the medical system 100. Alternatively, the clinic server 302, the biller server 406, the claim adjudication server 408, the training engine 508, and the machine learning models 510 may reside on the clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, any other suitable computer device or server, or any combination thereof.

The machine learning models 510 may include one or more neural networks, such as an image classifier, a recurrent neural network, a convolutional network, a generative adversarial network, a fully connected neural network, any other suitable network, or combination thereof. In some embodiments, the machine learning models 510 may be composed of a single level of linear or non-linear operations or may include multiple levels of non-linear operations. For example, the machine learning models 510 may include numerous layers and/or hidden layers that perform calculations (e.g., dot products) using various neural nodes.

Any of the medical system 100, the computing device 112 of the medical system 100, the clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, the training server 506, the training engine 508, any other suitable computing device, or any combination thereof may be configured to receive device-generated information from a medical device. The device-generated information may be information generated by the medical device. The medical device may include the medical device 102. The medical device 102 may include the medical system 100. The device-generated information can include information obtained by the electromechanical device 104, the sensor 106, the camera 108, the imaging device 110, any other portion of the medical device 102, any separate or remote electromechanical device, any separate or remote sensor, any separate remote camera, any separate or remote imaging device, any other suitable device, or any combination thereof. The device-generated information may include vital sign information, such as heart rate, blood oxygen content, blood pressure, or any other suitable vital sign. The device-generated information may include images, such as MM images, X-ray images, video camera images, still camera images, infrared images, or any other suitable images. The device-generated information may also include performance information (i.e., information relating to the physical performance of the user while the user operates a medical device), such as a rate of pedaling of a physical therapy cycle, a slope of a treadmill, a force applied to a strain-gauge, a weight lifted, a (simulated) distance traveled on a treadmill, or any other suitable performance information. The device-generated information may include medical device use information, such as a location of the medical device 102, a healthcare provider associated with the medical device 102, a practice group associated with the medical device 102, a time of day that the medical device 102 was used, a date that the medical device 102 was used, a duration that the medical device 102 was used, or any other suitable medical device use information.

Any of the medical system 100, the computing device 112 of the medical system 100, the clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, the training server 506, the training engine 508, any other suitable computing device, or any combination thereof may be configured to use the device-generated information to determine device-based medical coding information. Determining device-based medical coding information can include cross-referencing information about actions performed by or with the medical device 102 contained within the device-generated information with a reference list associating the actions performed by or with the medical device 102 with certain medical codes. The reference list can be stored on the clinic server 302, as part of the cloud-based learning system 504, or on any other suitable server, database, or system. Determining device-based medical coding information can include identifying a portion of the device-generated information containing medical coding information.

Any of the medical system 100, the computing device 112, the clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, the training server 506, the training engine 508, any other suitable computing device, or any combination thereof, may be configured to receive reviewed medical coding information. The reviewed medical coding information can include medical coding information reviewed or entered by a clinic operator. Reviewed medical coding information can include information about previously performed medical processes, procedures, surgeries, or any other suitable reviewed coding information. The reviewed medical coding information can be medical coding information that a clinic operator has reviewed on a computing device or entered into a computing device. For example, a surgeon can review and revise, on a computing device, medical coding information about a surgery that the surgeon performed on a patient (user).

Any of the medical system 100, the computing device 112 of the medical system 100, the clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, the training server 506, the training engine 508, any other suitable computing device, or any combination thereof may be configured to generate a predicted biometric signature (i.e., a first biometric signature). The predicted biometric signature may include and/or be determined by a kinesiological signature. For example, the predicted biometric signature can include a predicted movement such as a range of motion of a user's joint, such as a knee, an elbow, a neck, a spine, or any other suitable joint or muscle of a human. The predicted biometric signature may be based at least in part on historical information. In an example where a patient is using a physical therapy cycle 200, such cycle preferably located at the patient's home or residence, as part of telemedicine-enabled or -mediated rehabilitation therapy, then, using past camera images of the user taken by the device, the predicted biometric signature can include an expected image of the user. The predicted biometric signature may be based at least in part on the reviewed medical coding information. For example, where a user has undergone a specific back surgery, the predicted biometric signature may include an MM image of the user's upper back, such image showing evidence of that surgery. The predicted biometric signature may be based at least in part on the device-based medical coding information. For example, if the device-based medical coding information indicates that the user has undergone an upper-back MM, the predicted biometric signature may be based at least in part on how the image of the upper back is expected to appear based on other historical information, such as past surgeries identified using the reviewed medical coding information. The predicted biometric signature may be based at least in part on Electronic Medical Records (EMRs). For example, the predicted biometric signature may be based at least in part on a height value and a weight value entered into the EMRs. The predicted biometric signature may be based at least in part on historical performance information (i.e., performance information generated in the past relating to a specific user or other users). For example, the predicted biometric signature may be based at least in part on a determination that a patient's performance on the physical therapy cycle 200 should be within a certain range of the patient's last performance on the physical therapy cycle 200. The determination may be modified using the amount of time since the patient has last used the physical therapy cycle 200. The predicted biometric signature may be derived from any other suitable information, or any combination of any of the previous examples of information from which the predicted biometric signature is derived. Further, if the predicted biometric signature includes a kinesiological signature, the predicted biometric signature may be derived from any other suitable information, or any combination of any of the previous examples of information from which the predicted biometric signature is derived. For example, reviewed medical coding information relating to a knee surgery may be used to determine knee joint motion.

Any of the medical system 100, the computing device 112 of the medical system 100, the clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, the training server 506, the training engine 508, any other suitable computing device, or any combination thereof may be configured to, using the device-generated information, generate a device-based biometric signature (i.e., a second biometric signature). The device-based biometric signature may be a kinesiological signature. For example, the device-based biometric signature can include the movement and joint range of a user's knee. The device-based biometric signature may be based at least in part on the device-based medical coding information. For example, where the device-based medical coding information suggests that the user has undergone an upper-back MM, the device-based biometric signature may be based at least in part on the device-generated information about the upper back. The device-based biometric signature may be based at least in part on the performance information. For example, the device-based biometric signature may be derived from a rate of pedaling of a physical therapy cycle 200, a slope of a treadmill, a force applied to a strain-gauge, a weight lifted, a (simulated) distance traveled on a treadmill, or any other suitable performance information. The device-based biometric signature may be derived from images included in the device-generated information, such as MM images, X-ray images, video camera images, still camera images, infrared images, or any other suitable images. The device-based biometric signature may be derived from any other suitable information, or any combination of any of the previous examples of information upon with the device-based biometric signature is based. Further, if the device-based biometric signature includes a kinesiological signature, the device-based biometric signature may be derived from any other suitable information, or any combination of any of the previous examples of information upon with the device-based biometric signature is based. For example, camera images may be used to determine knee joint motion as a kinesiological signature embodiment of the device-based biometric signature.

Any of the medical system 100, the computing device 112 of the medical system 100, clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, the training server 506, the training engine 508, any other suitable computing device, or any combination thereof may be configured to use the predicted biometric signature and the device-based biometric signature to generate a signature comparison. The signature comparison can include differences in terms of degrees between the predicted biometric signature and the device-based biometric signature. For example, if the predicted biometric signature includes height information for a user with a value of 5 feet 4 inches and the device-based biometric signature includes height information for a user with a value of 5 feet 5 inches, the degree of difference between the predicted biometric signature and the device-based biometric signature may be indicated to be below a FWA threshold value. However, if the predicted biometric signature includes height information for a user with a value of 5 feet 4 inches and the device-based biometric signature includes height information for a user with a value of 5 feet 9 inches tall, the degree of difference between the predicted biometric signature and the device-based biometric signature may be noted to be above the FWA threshold value.

Any of the medical system 100, the computing device 112 of the medical system 100, the clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, the training server 506, the training engine 508, any other suitable computing device, or any combination thereof may be configured to use the signature comparison to generate a signature indicator. To indicate an incorrect user, the signature indicator can include flagging when the signature comparison is outside an acceptable user threshold. For example, if the predicted biometric signature includes height information for a user with a height value of 5 feet 4 inches tall and the device-based biometric signature includes height information for a user with a value of 5 feet 9 inches tall, a signature indicator may be generated. The signature indicator may indicate that the difference between the predicted biometric signature and the device-based biometric signature is above the FWA threshold value. This difference may be the result of an incorrect user using the medical device. Another example includes generating a signature indicator in response to differences in between the predicted biometric signature and the device-based biometric signature, as derived from the performance metric information and the vital sign information, such that the processor 114 determines that the differences are above a FWA threshold. In response to this determination, the processor 114 generates the signature indicator. In this example, a post-knee surgery user walked a mile in 45 minutes on a treadmill with an average heartrate of 190 beats per minute (bpm) (i.e., the user struggled to walk a mile) and the same user later walked 5 miles on the treadmill in 45 minutes with a heartrate of 130 bpm (i.e., the user did not struggle to walk more than a mile in the same time). Another example includes a camera image displaying different images of users for the same billing user, as determined by using facial recognition software. Another example includes a user with a low range of movement in his knee joint on a first day and the same user with a high range of movement in his knee joint on a consecutive day (i.e., a kinesiological signature above the FWA threshold). The signature indicator can include flagging if the differences are determined to be the result of any errors or inconsistencies in the EMRs or reviewed medical coding information. For example, if the predicted biometric signature is based on a certain type of surgery, and the device-based biometric signature is not consistent with such surgery (i.e., consistent with a less-intense surgery—perhaps one not requiring as intense or expensive a physical therapy regimen), a signature indicator may be generated. The signature indicator may be transmitted to an operator to indicate that there is an error or an inconsistency in the EMRs or reviewed medical coding information.

Any of the medical system 100, the computing device 112, the clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, the training server 506, the training engine 508, any other suitable computing device, or any combination thereof may be configured to transmit the signature indicator. For example, any of the medical system 100, the computing device 112 of the medical system 100, the clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, the training server 506, the training engine 508, any other suitable computing device, or any combination thereof may transmit the signature indicator (e.g., a flag) to the medical system 100, the computing device 112 of the medical system 100, clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, the training server 506, the training engine 508, any other suitable computing device, or any combination thereof.

The signature indicator may be used by the receiving system or the server. In one exemplary embodiment, at the medical system 100, the signature indicator can be used to validate information and/or to set a flag to inform an operator of the medical system 100 or medical device 102 that there is a biometric signature mismatch and, for example, the wrong therapy may have been prescribed to a patient. In another exemplary embodiment, the clinic server 302 can use the signature indicator to validate information and/or to determine whether to transmit a message to an operator or administrator. The message may include information indicating a biometric signature mismatch and/or information improperly entered into the EMR database 404. In another exemplary embodiment, the biller server 406 may use the signature indicator to validate information received or sent and/or to not send the medical coding information to the claim adjudication server 408 until the biometric signature is matched. In another exemplary embodiment, the claim adjudication server 408 may use the may use the signature indicator to (1) validate information received; (2) determine that a flag should be added to the medical coding information prior to transmitting the medical coding information to the FWA server 410 and/or the payment server 412; or (3) receive additional information from the FWA server 410. In another exemplary embodiment, the FWA server 410 can use the signature indicator to (1) validate information received, (2) determine whether to transmit a message, and/or (3) make a determination of whether to flag the medical coding information as fraudulent and transmit a message to initiate a FWA investigation. In another exemplary embodiment, the payment server 412 can use the signature indicator to validate information received and/or to determine whether to pay the medical service provider. In another exemplary embodiment, the training server 506 and/or the training engine 508 can use the signature indicator for further machine learning activities (i.e., by increasing the size of the dataset every time a signature indicator is generated).

Any of the medical system 100, the computing device 112 of the medical system 100, the clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, the training server 506, the training engine 508, any other suitable computing device, or any combination thereof may be configured to generate an emergency biometric signature for use in detecting and responding to an emergency event. When a user is undergoing telemedicine-enabled or -mediated rehabilitation therapy without direct supervision by a trained medical professional, automatically (including, without limitation, through means of artificial intelligence and/or machine learning) recognizing and responding to emergency events may be desirable in the event that an emergency situation occurs. The emergency biometric signature can be derived from the predicted biometric signature. The emergency biometric signature may include vital sign information (a user's heart rate or blood pressure being too high or too low), imagery (a user's face turning purple), or any other suitable information. In an example where a patient is using a physical therapy cycle 200 located at the patient's home or residence to undergo telemedicine-enabled or -mediated rehabilitation therapy, the emergency biometric signature can include a value of a heart-rate of a user that is above an emergency threshold value. The emergency threshold may be derived from the predicted biometric signature. The value above the emergency threshold value may indicate an emergency condition. The emergency biometric signature can include a kinesiological signature, such as where the emergency biometric signature includes a knee joint having a range of greater than 180°. Non-limiting examples of emergency conditions include broken bones, heart attacks, and blood loss.

Any of the medical system 100, the computing device 112, the clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, the training server 506, the training engine 508, any other suitable computing device, or any combination thereof may be configured to use the device-based biometric signature and/or an emergency biometric signature to generate an emergency comparison. The emergency comparison can be derived from vital sign information, imagery, or any other suitable information. For example, a device-based biometric signature including a heart rate value of 0 bpm can be compared to an emergency biometric signature including an emergency range of heart rate values of 0-40 bpm. In this example, the emergency comparison indicates that the device-based biometric signature heart rate is within the emergency range. As another example, a device-based biometric signature including a user's face being a shade of purple can be compared to an emergency biometric signature including an emergency range of shades of the user's face. In this example, the emergency comparison indicates that the shade of the user's face is within the emergency range. As yet another example, a device-based biometric signature in which the range of motion of the user's joint has extended to 270° can be compared to an emergency biometric signature in which an emergency range of knee joint extension includes values greater than 180°. In this example, the emergency comparison indicates that the knee joint range is in the emergency range.

Any of the medical system 100, the computing device 112, the clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, the training server 506, the training engine 508, any other suitable computing device, or any combination thereof may be configured to use the emergency comparison to generate an emergency indicator. The emergency indicator can include whether an emergency biometric signature matches a device-based biometric signature. Examples of the emergency indicators include flags and saved variables. For example, the emergency indicator can be generated when the comparison indicates a similarity or overlap between the device-based biometric signature and the emergency biometric signature. For example, the emergency indicator can be derived from the emergency comparison if the emergency comparison indicates that the knee joint range is in the emergency range.

Any of the medical system 100, the computing device 112, the clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, the training server 506, the training engine 508, any other suitable computing device, or any combination thereof may be configured to transmit the emergency indicator. For example, any of the medical system 100, the computing device 112 of the medical system 100, the clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, the training server 506, the training engine 508, any other suitable computing device, or any combination thereof may transmit the emergency indicator to the medical system 100, the computing device 112 of the medical system 100, the clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, the training server 506, the training engine 508, an emergency services system or computer, any other suitable computing device, or any combination thereof. Further, the biometric information may also be transmitted to provide emergency or clinic services with information about the nature of the emergency. Further, the medical system 100, the computing device 112 of the medical system 100, the clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, the training server 506, the training engine 508, an emergency services system or computer, any other suitable computing device, or any combination thereof can activate an output device 120, such as an alarm system. The alarm system can include a speaker, a siren, a system that contacts emergency services (e.g., to summon an ambulance), a flashing light, any other suitable alarm component, or any combination thereof.

FIG. 5 is not intended to be limiting; the medical claim processing system 500, the medical system 100, computing device 112, the clinic server 302, the clinic server 302, the computing device 304, the cloud-based learning system 504, and any sub-components thereof may include more or fewer components than those illustrated in FIG. 5.

FIGS. 6A and 6B illustrate a computer-implemented method 600 for processing medical claims. The method 600 may be performed on the medical system 100, the computing device 112, the clinic server 302, the biller server 406, the claim adjudication server 408, the FWA server 410, the payment server 412, the training server 506, the training engine 508, any other suitable computing device, or any combination thereof. The method 600 may be implemented on a processor, such as the processor 306, configured to perform the steps of the method 600. The method 600 may be implemented on a system, such as the medical system 100 or the clinic server system 300, that includes a processor, such as the processor 306, and a memory device, such as the memory device 308. The method 600 may be implemented on the clinic server system 300. The method 600 may include operations that are implemented in instructions stored in a memory device, such as the memory device 308, and executed by a processor, such as the processor 306, of a computing device, such as the computing device 304. The steps of the method 600 may be stored in a non-transient computer-readable storage medium.

At step 602, the method 600 can include receiving device-generated information from a medical device, such as the medical device 102. For example, the clinic server 302 can receive (1) knee angle information from a goniometer attached to a knee of a user of the physical therapy cycle 200; and (2) pedal speed information and force information from the physical therapy cycle 200. After the clinic server 302 receives the device-generated information from the medical device 102, the clinic server 302 can proceed to step 604 or to step 610. Alternatively, the clinic server 302 can proceed to steps 604 and 610.

At step 604, the method 600 can include using the device-generated information to determine device-based medical coding information. For example, the clinic server 302 can use the pedal speed information and/or force information from the physical therapy cycle to determine that the user is undergoing a one-hour therapy session. The clinic server 302 can access the EMRs associated with the user to determine which information is relevant to the therapy session (e.g., that the user has a prior right knee injury). The clinic server 302 can determine medical coding information associated with one-hour therapy sessions for a right knee injury. After the clinic server 302 determines the device-based medical information, the clinic server 302 can proceed to step 606.

At step 606, the method 600 can include receiving reviewed medical coding information. For example, the clinic server 302 can receive information input by a doctor that the user has an injury to the user's left knee. After the clinic server 302 receives the reviewed medical coding information, the clinic server 302 can proceed to step 608.

At step 608, the method 600 can include receiving electronic medical records (EMRs) for a user of a medical device 102. For example, the clinic server 302 can receive information from the EMRs. The information can indicate that the user has an injury to the user's left knee. After the clinic server 302 receives the EMRs, the clinic server 302 can proceed to step 610.

At step 610, the method 600 can include generating a first biometric signature (i.e., a predicted biometric signature). The clinic server 302 can generate the first biometric signature. The first biometric signature may be a kinesiological signature of a user. For example, the clinic server 302 can use the injury and the past performance of the user to generate a first biometric signature, which may include a first kinesiological signature (i.e., an emergency kinesiological signature) having a predicted left knee joint range of motion between approximately 130°-140° and a predicted right knee joint range of motion between approximately 165-170°. After the clinic server 302 generates the first biometric signature, the clinic server 302 can proceed to step 612.

At step 612, the method 600 can include generating, using the device-generated information, a second biometric signature (i.e., a device-based biometric signature). The second biometric signature may be a kinesiological signature. For example, the clinic server 302 can generate, using the measurements from the goniometer, a second biometric signature including a second kinesiological signature (i.e., a device-based kinesiological signature) having a left knee joint range of motion of approximately 170° and a right knee joint range of motion of approximately 135°. After the clinic server 302 generates the second biometric signature, the clinic server 302 can proceed to step 614.

At step 614, the method 600 can include comparing the first and second biometric signatures. For example, the clinic server 302 can compare the predicted left knee joint range of motion (i.e., the first biometric signature having a predicted a range of motion of approximately) 130°-140° and the measured a left knee joint range of motion (i.e., the second biometric signature with a measured range of motion of approximately 170°). After the clinic server 302 generates compares the first and second biometric signatures, the clinic server 302 can proceed to step 616.

At step 616, the method 600 can include generating, using the first biometric signature and the second biometric signature, a signature comparison. For example, the clinic server 302 can generate a signature comparison showing that the user's left knee joint range of motion is outside of the expected range of motion for the user's left knee joint (e.g., approximately 30° above the expected maximum range of motion). The clinic server 302 can generate one or more signature comparisons. For example, the clinic server 302 can generate a second signal comparison that the user's right knee joint range of motion is outside of the expected range of motion for the user's right knee joint (e.g., approximately 30° below the expected minimum range of motion). After the clinic server 302 generates the signature comparison, the clinic server 302 can proceed to step 618.

At step 618, the method 600 can include generating, using the signature comparison, a signature indicator (e.g., a variable or flag that indicates whether the differences between the first and second biometric signatures exceed a FWA threshold value). The signature indicator can include flagging if the differences are determined to be the result of an incorrect user. For example, the clinic server 302 can use the left knee joint range of motion being outside of an expected range of motion threshold to generate a signature indicator flagging that the user may be an incorrect user, that there may be an error in the medical records, that the goniometer measurements may have been incorrect (e.g., another user's medical records) resulting from an operator error, or that any other suitable error has occurred. After the clinic server 302 generates the signature indicator, the clinic server 302 can proceed to step 620.

At step 620, the method 600 can include transmitting the signature indicator. For example, the clinic server 302 may transmit the signature indicator to the biller server 406. After the clinic server 302 transmits the signature indicator, the clinic server 302 can end the method or proceed to step 622.

At step 622, the method 600 can include generating an emergency biometric signature including information indicative of an emergency event (e.g., a heart attack, broken bone, blood loss, etc.). For example, the clinic server 302 can generate an emergency biometric signature having a knee joint range of motion in excess of 185°. After the clinic server 302 generates the emergency biometric signature, the clinic server 302 can proceed to step 624.

At step 624, the method 600 can include using the second biometric signature and the emergency biometric signature to generate an emergency comparison. For example, if the emergency biometric signature is generated when a knee joint range of motion of a user operating the physical therapy cycle 200 is greater than an emergency threshold of 185° and the second biometric signature determines that a knee joint range of motion of a user operating the physical therapy cycle 200 is approximately 270°, the user has exceeded the emergency threshold and the clinic server 302 can generate the emergency comparison. After the clinic server 302 generates the emergency comparison, the clinic server 302 can proceed to step 626.

At step 626, the method 600 can include, using the emergency comparison to generate an emergency indicator. For example, using the second biometric signature having a knee joint range of motion exceeding the emergency threshold of the emergency biometric signature (e.g., the user's range of motion is 85° greater than the emergency biometric signature), the clinic server 302 can determine that there is an emergency condition. After the clinic server 302 generates the emergency indicator, the clinic server 302 can proceed to step 628.

At step 628, the method 600 can include transmitting the emergency indicator. For example, in response to the generation of the emergency indicator, the clinic server 302 can transmit the emergency indicator to an on-site registered nurse. The emergency indicator may include information, device-generated information, EMRs, the emergency comparison, any other suitable information, or any combination thereof.

FIGS. 6A and 6B are not intended to be limiting; the method 600 can include more or fewer steps and/or processes than those illustrated in FIG. 6. Further, the order of the steps of the method 600 is not intended to be limiting; the steps can be arranged in any suitable order. Any or all of the steps of method 600 may be implemented during a telemedicine session or at any other desired time.

FIG. 10 shows an example computer system 800 which can perform any one or more of the methods described herein, in accordance with one or more aspects of the present disclosure. In one example, computer system 800 may include a computing device and correspond to an assistance interface, a reporting interface, a supervisory interface, a clinician interface, a server (including an AI engine), a patient interface, an ambulatory sensor, a goniometer, a treatment device 10, a medical device 102, a pressure sensor, or any suitable component. The computer system 800 may be capable of executing instructions implementing the one or more machine learning models of the artificial intelligence engine. The computer system may be connected (e.g., networked) to other computer systems in a LAN, an intranet, an extranet, or the Internet, including via the cloud or a peer-to-peer network. The computer system may operate in the capacity of a server in a client-server network environment. The computer system may be a personal computer (PC), a tablet computer, a wearable (e.g., wristband), a set-top box (STB), a personal Digital Assistant (PDA), a mobile phone, a camera, a video camera, an Internet of Things (IoT) device, or any device capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that device. Further, while only a single computer system is illustrated, the term “computer” shall also be taken to include any collection of computers that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methods discussed herein.

The computer system 800 includes a processing device 802, a main memory 804 (e.g., read-only memory (ROM), flash memory, solid state drives (SSDs), dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM)), a static memory 806 (e.g., flash memory, solid state drives (SSDs), static random access memory (SRAM)), and a data storage device 808, which communicate with each other via a bus 810.

Processing device 802 represents one or more general-purpose processing devices such as a microprocessor, central processing unit, or the like. More particularly, the processing device 802 may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, or a processor implementing other instruction sets or processors implementing a combination of instruction sets. The processing device 802 may also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a system on a chip, a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like. The processing device 802 is configured to execute instructions for performing any of the operations and steps discussed herein.

The computer system 800 may further include a network interface device 812. The computer system 800 also may include a video display 814 (e.g., a liquid crystal display (LCD), a light-emitting diode (LED), an organic light-emitting diode (OLED), a quantum LED, a cathode ray tube (CRT), a shadow mask CRT, an aperture grille CRT, a monochrome CRT), one or more input devices 816 (e.g., a keyboard and/or a mouse or a gaming-like control), and one or more speakers 818 (e.g., a speaker). In one illustrative example, the video display 814 and the input device(s) 816 may be combined into a single component or device (e.g., an LCD touch screen).

The data storage device 816 may include a computer-readable medium 820 on which the instructions 822 embodying any one or more of the methods, operations, or functions described herein is stored. The instructions 822 may also reside, completely or at least partially, within the main memory 804 and/or within the processing device 802 during execution thereof by the computer system 800. As such, the main memory 804 and the processing device 802 also constitute computer-readable media. The instructions 822 may further be transmitted or received over a network via the network interface device 812.

While the computer-readable storage medium 820 is shown in the illustrative examples to be a single medium, the term “computer-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “computer-readable storage medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present disclosure. The term “computer-readable storage medium” shall accordingly be taken to include, but not be limited to, solid-state memories, optical media, and magnetic media.

FIG. 10 is not intended to be limiting; the system 800 may include more or fewer components than those illustrated in FIG. 10.

The term “computer-readable storage medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “computer-readable storage medium” shall also be taken to include any medium capable of storing, encoding or carrying a set of instructions for execution by the machine and causing the machine to perform any one or more of the methodologies of the present disclosure. The term “computer-readable storage medium” shall accordingly be taken to include, but not be limited to, solid-state memories, optical media, and magnetic media.

Any of the systems and methods described in this disclosure may be used in connection with rehabilitation. Unless expressly stated otherwise, is to be understood that rehabilitation includes prehabilitation (also referred to as “pre-habilitation” or “prehab”). Prehabilitation may be used as a preventative procedure or as a pre-surgical or pre-treatment procedure. Prehabilitation may include any action performed by or on a patient (or directed to be performed by or on a patient, including, without limitation, remotely or distally through telemedicine) to, without limitation, prevent or reduce a likelihood of injury (e.g., prior to the occurrence of the injury); improve recovery time subsequent to surgery; improve strength subsequent to surgery; or any of the foregoing with respect to any non-surgical clinical treatment plan to be undertaken for the purpose of ameliorating or mitigating injury, dysfunction, or other negative consequence of surgical or non-surgical treatment on any external or internal part of a patient's body. For example, a mastectomy may require prehabilitation to strengthen muscles or muscle groups affected directly or indirectly by the mastectomy. As a further non-limiting example, the removal of an intestinal tumor, the repair of a hernia, open-heart surgery or other procedures performed on internal organs or structures, whether to repair those organs or structures, to excise them or parts of them, to treat them, etc., can require cutting through and harming numerous muscles and muscle groups in or about, without limitation, the abdomen, the ribs and/or the thoracic cavity. Prehabilitation can improve a patient's speed of recovery, measure of quality of life, level of pain, etc. in all the foregoing procedures. In one embodiment of prehabilitation, a pre-surgical procedure or a pre-non-surgical-treatment may include one or more sets of exercises for a patient to perform prior to such procedure or treatment. The patient may prepare an area of his or her body for the surgical procedure by performing the one or more sets of exercises, thereby strengthening muscle groups, improving existing and/or establishing new muscle memory, enhancing mobility, improving blood flow, and/or the like.

In some embodiments, the systems and methods described herein may use artificial intelligence and/or machine learning to generate a prehabilitation treatment plan for a user. Additionally, or alternatively, the systems and methods described herein may use artificial intelligence and/or machine learning to recommend an optimal exercise machine configuration for a user. For example, a data model may be trained on historical data such that the data model may be provided with input data relating to the user and may generate output data indicative of a recommended exercise machine configuration for a specific user. Additionally, or alternatively, the systems and methods described herein may use machine learning and/or artificial intelligence to generate other types of recommendations relating to prehabilitation, such as recommended reading material to educate the patient, a recommended health professional specialist to contact, and/or the like.

Consistent with the above disclosure, the examples of systems and method enumerated in the following clauses are specifically contemplated and are intended as a non-limiting set of examples.

Clause 1. A computer-implemented system for processing medical claims, comprising:

a medical device configured to be manipulated by a user while the user performs a treatment plan;

a patient interface associated with the medical device, the patient interface comprising an output configured to present telemedicine information associated with a telemedicine session; and

a processor configured to:

-   -   during the telemedicine session, receive device-generated         information from the medical device;     -   generate a first biometric signature;     -   using the device-generated information, generate a second         biometric signature;     -   using the first and second biometric signatures, generate a         signature comparison;     -   using the signature comparison, generate a signature indicator;         and     -   transmit the signature indicator.

Clause 2. The computer-implemented system of any clause herein, wherein:

the device-generated information is generated by the medical device;

using the device-generated information, the processor is further configured to determine device-based medical coding information; and

generating the second biometric signature uses the device-based medical coding information.

Clause 3. The computer-implemented system of any clause herein, wherein the processor is further configured to receive reviewed medical coding information; and

wherein generating the first biometric signature uses the reviewed medical coding information.

Clause 4. The computer-implemented system of any clause herein, wherein the processor is further configured to receive electronic medical records pertaining to the user of the medical device; and

wherein generating the first biometric signature uses the electronic medical records.

Clause 5. The computer-implemented system of any clause herein, wherein the processor is further configured to:

using the second biometric signature and an emergency biometric signature, generate an emergency comparison;

using the emergency comparison, generate an emergency indicator; and

transmit the emergency indicator.

Clause 6. A system for processing medical claims, comprising:

a processor configured to:

-   -   receive device-generated information from a medical device;     -   generate a first biometric signature;     -   using the device-generated information, generate a second         biometric signature;     -   using the first biometric signature and the second biometric         signature, compare the signatures;     -   using the first and second biometric signatures, generate a         signature comparison;     -   using the signature comparison, generate a signature indicator;         and     -   transmit the signature indicator.

Clause 7. The system of any clause herein, wherein the device-generated information is generated by the medical device.

Clause 8. The system of any clause herein, wherein, using the device-generated information, the processor is further configured to determine device-based medical coding information; and

wherein generating the second biometric signature uses the device-based medical coding information.

Clause 9. The system of any clause herein, wherein the processor is further configured to receive reviewed medical coding information; and

wherein generating the first biometric signature uses the reviewed medical coding information.

Clause 10. The system of any clause herein, wherein the processor is further configured to receive electronic medical records pertaining to a user of the medical device; and

wherein generating the first biometric signature uses the electronic medical records.

Clause 11. The system of any clause herein, wherein the processor is further configured to:

using the second biometric signature and an emergency biometric signature, generate an emergency comparison;

using the emergency comparison, generate an emergency indicator; and

transmit the emergency indicator.

Clause 12. The system of any clause herein, wherein the processor is further configured to generate the emergency biometric signature.

Clause 13. The system of any clause herein, wherein the device-generated information includes at least one of vital sign information, images, and medical device use information.

Clause 14. The system of any clause herein, wherein the device-generated information includes performance information; and

wherein generating the second biometric signature uses the performance information.

Clause 15. The system of any clause herein, wherein generating the first biometric signature uses historical performance information.

Clause 16. The system of any clause herein, wherein the first biometric signature includes a first kinesiological signature; and

wherein the second biometric signature includes a second kinesiological signature.

Clause 17. The system of any clause herein, further comprising a memory device operatively coupled to the processor, wherein the memory device stores instructions, and wherein the processor is configured to execute the instructions.

Clause 18. A method for processing medical claims, comprising:

receiving device-generated information from a medical device;

generating a first biometric signature;

using the device-generated information, generating a second biometric signature;

using the first biometric signature and the second biometric signature, generating a signature comparison;

using the signature comparison, generating a signature indicator; and

transmitting the signature indicator.

Clause 19. The method of any clause herein, wherein the device-generated information is generated by the medical device.

Clause 20. The method of any clause herein, further comprising using the device-generated information to determine device-based medical coding information;

wherein generating the second biometric signature uses the device-based medical coding information.

Clause 21. The method of any clause herein, further comprising receiving reviewed medical coding information; wherein generating the first biometric signature uses the reviewed medical coding information.

Clause 22. The method of any clause herein, further comprising receiving electronic medical records pertaining to a user of the medical device; wherein generating the first biometric signature uses the electronic medical records.

Clause 23. The method of any clause herein, further comprising:

using the second biometric signature and an emergency biometric signature to generate an emergency comparison;

using the emergency comparison to generate an emergency indicator; and

transmitting the emergency indicator.

Clause 24. The method of any clause herein, further comprising generating the emergency biometric signature.

Clause 25. The method of any clause herein, wherein the device-generated information includes at least one of vital sign information, images, and medical device use information.

Clause 26. The method of any clause herein, wherein the device-generated information includes performance information; and

wherein generating the second biometric signature uses the performance information.

Clause 27. The method of any clause herein, wherein generating the first biometric signature uses historical performance information.

Clause 28. The method of any clause herein, wherein the first biometric signature includes a first kinesiological signature; and

wherein the second biometric signature includes a second kinesiological signature.

Clause 29. A tangible, non-transitory computer-readable storage medium storing instructions that, when executed, cause a processor to:

receive device-generated information from a medical device;

generate a first biometric signature;

using the device-generated information, generate a second biometric signature;

using the first biometric signature and the second biometric signature, generate a signature comparison;

using the signature comparison, generate a signature indicator; and

transmit the signature indicator.

Clause 30. The tangible, non-transitory computer-readable storage medium of any clause herein, wherein the device-generated information is generated by the medical device.

Clause 31. The tangible, non-transitory computer-readable storage medium of any clause herein, wherein using the device-generated information, the instructions further cause the processor to determine device-based medical coding information; and

wherein generating the second biometric signature uses the device-based medical coding information.

Clause 32. The tangible, non-transitory computer-readable storage medium of any clause herein, wherein the instructions further cause the processor to receive electronic medical records pertaining to a user of the medical device; and

wherein generating the first biometric signature uses the electronic medical records.

Clause 33. The tangible, non-transitory computer-readable storage medium of any clause herein, wherein the instructions further cause the processor to:

using the second biometric signature and an emergency biometric signature, generate an emergency comparison;

using the emergency comparison, generate an emergency indicator; and

transmit the emergency indicator.

Clause 34. The tangible, non-transitory computer-readable storage medium of any clause herein, wherein the instructions further cause the processor to generate the emergency biometric signature.

Clause 35. The tangible, non-transitory computer-readable storage medium of any clause herein, wherein the device-generated information includes at least one of vital sign information, images, and medical device use information.

Clause 36. The tangible, non-transitory computer-readable storage medium of any clause herein, wherein the device-generated information includes performance information; and

wherein generating the second biometric signature uses the performance information.

Clause 37. The tangible, non-transitory computer-readable storage medium of any clause herein, wherein the device-generated information includes performance information; and

wherein generating the second biometric signature uses the performance information.

Clause 38. The tangible, non-transitory computer-readable storage medium of any clause herein, wherein generating the first biometric signature uses historical performance information.

Clause 39. The tangible, non-transitory computer-readable storage medium of any clause herein, wherein the first biometric signature includes a first kinesiological signature; and

wherein the second biometric signature includes a second kinesiological signature.

No part of the description in this application should be read as implying that any particular element, step, or function is an essential element that must be included in the claim scope. The scope of patented subject matter is defined only by the claims. Moreover, none of the claims is intended to invoke 35 U.S.C. § 112(f) unless the exact words “means for” are followed by a participle.

The foregoing description, for purposes of explanation, use specific nomenclature to provide a thorough understanding of the described embodiments. However, it should be apparent to one skilled in the art that the specific details are not required to practice the described embodiments. Thus, the foregoing descriptions of specific embodiments are presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the described embodiments to the precise forms disclosed. It should be apparent to one of ordinary skill in the art that many modifications and variations are possible in view of the above teachings.

The above discussion is meant to be illustrative of the principles and various embodiments of the present invention. Once the above disclosure is fully appreciated, numerous variations and modifications will become apparent to those skilled in the art. It is intended that the following claims be interpreted to embrace all such variations and modifications. 

What is claimed is:
 1. A computer-implemented system for processing medical claims, comprising: a medical device configured to be manipulated by a user while the user performs a treatment plan; a patient interface associated with the medical device, the patient interface comprising an output configured to present telemedicine information associated with a telemedicine session; and a processor configured to: during the telemedicine session, receive device-generated information from the medical device; generate a first biometric signature; using the device-generated information, generate a second biometric signature; using the first and second biometric signatures, generate a signature comparison; using the signature comparison, generate a signature indicator; and transmit the signature indicator.
 2. The computer-implemented system of claim 1, wherein: the device-generated information is generated by the medical device; using the device-generated information, the processor is further configured to determine device-based medical coding information; and generating the second biometric signature uses the device-based medical coding information.
 3. The computer-implemented system of claim 1, wherein the processor is further configured to receive reviewed medical coding information; and wherein generating the first biometric signature uses the reviewed medical coding information.
 4. The computer-implemented system of claim 1, wherein the processor is further configured to receive electronic medical records pertaining to the user of the medical device; and wherein generating the first biometric signature uses the electronic medical records.
 5. The computer-implemented system of claim 1, wherein the processor is further configured to: using the second biometric signature and an emergency biometric signature, generate an emergency comparison; using the emergency comparison, generate an emergency indicator; and transmit the emergency indicator.
 6. A system for processing medical claims, comprising: a processor configured to: receive device-generated information from a medical device; generate a first biometric signature; using the device-generated information, generate a second biometric signature; using the first and second biometric signatures, generate a signature comparison; using the signature comparison, generate a signature indicator; and transmit the signature indicator.
 7. The system of claim 6, wherein the device-generated information is generated by the medical device.
 8. The system of claim 6, wherein, using the device-generated information, the processor is further configured to determine device-based medical coding information; and wherein generating the second biometric signature uses the device-based medical coding information.
 9. The system of claim 8, wherein the processor is further configured to generate the emergency biometric signature.
 10. The system of claim 6, wherein the device-generated information includes at least one of vital sign information, images, and medical device use information.
 11. The system of claim 6, wherein the device-generated information includes performance information; and wherein generating the second biometric signature uses the performance information.
 12. The system of claim 6, wherein generating the first biometric signature uses historical performance information.
 13. The system of claim 6, wherein the first biometric signature includes a first kinesiological signature; and wherein the second biometric signature includes a second kinesiological signature.
 14. A method for processing medical claims, comprising: receiving device-generated information from a medical device; generating a first biometric signature; using the device-generated information, generating a second biometric signature; using the first biometric signature and the second biometric signature, generating a signature comparison; using the signature comparison, generating a signature indicator; and transmitting the signature indicator.
 15. The method of claim 14, wherein the device-generated information is generated by the medical device.
 16. The method of claim 14, further comprising using the device-generated information to determine device-based medical coding information; wherein generating the second biometric signature uses the device-based medical coding information.
 17. The method of claim 14, further comprising receiving reviewed medical coding information; wherein generating the first biometric signature uses the reviewed medical coding information.
 18. The method of claim 14, further comprising receiving electronic medical records pertaining to a user of the medical device; wherein generating the first biometric signature uses the electronic medical records.
 19. The method of claim 14, further comprising: using the second biometric signature and an emergency biometric signature to generate an emergency comparison; using the emergency comparison to generate an emergency indicator; and transmitting the emergency indicator.
 20. The method of claim 19, further comprising generating the emergency biometric signature.
 21. The method of claim 14, wherein the device-generated information includes at least one of vital sign information, images, and medical device use information.
 22. The method of claim 14, wherein the device-generated information includes performance information; and wherein generating the second biometric signature uses the performance information.
 23. The method of claim 14, wherein generating the first biometric signature uses historical performance information.
 24. The method of claim 14, wherein the first biometric signature includes a first kinesiological signature; and wherein the second biometric signature includes a second kinesiological signature.
 25. A tangible, non-transitory computer-readable storage medium storing instructions that, when executed, cause a processor to: receive device-generated information from a medical device; generate a first biometric signature; using the device-generated information, generate a second biometric signature; using the first biometric signature and the second biometric signature, generate a signature comparison; using the signature comparison, generate a signature indicator; and transmit the signature indicator.
 26. The tangible, non-transitory computer-readable storage medium of claim 25, wherein the instructions further cause the processor to receive electronic medical records pertaining to a user of the medical device; and wherein generating the first biometric signature uses the electronic medical records.
 27. The tangible, non-transitory computer-readable storage medium of claim 25, wherein the instructions further cause the processor to: using the second biometric signature and an emergency biometric signature, generate an emergency comparison; using the emergency comparison, generate an emergency indicator; and transmit the emergency indicator.
 28. The tangible, non-transitory computer-readable storage medium of claim 25, wherein the device-generated information includes performance information; and wherein generating the second biometric signature uses the performance information.
 29. The tangible, non-transitory computer-readable storage medium of claim 25, wherein the device-generated information includes performance information; and wherein generating the second biometric signature uses the performance information.
 30. The tangible, non-transitory computer-readable storage medium of claim 25, wherein generating the first biometric signature uses historical performance information. 